feat(registry): add SPAKE2 (RFC 9382) and SPAKE2+ (RFC 9383)#798
Open
Mehrn0ush wants to merge 1 commit intoCycloneDX:masterfrom
Open
feat(registry): add SPAKE2 (RFC 9382) and SPAKE2+ (RFC 9383)#798Mehrn0ush wants to merge 1 commit intoCycloneDX:masterfrom
Mehrn0ush wants to merge 1 commit intoCycloneDX:masterfrom
Conversation
Member
|
cc: @bhess |
stevespringett
added
cap: cryptography
bhess
reviewed
Feb 12, 2026
schema/cryptography-defs.json
Outdated
| ], | ||
| "variant": [ | ||
| { | ||
| "pattern": "SPAKE2", |
Contributor
There was a problem hiding this comment.
This patterns seems redundant since the pattern below already covers it.
schema/cryptography-defs.json
Outdated
| ], | ||
| "variant": [ | ||
| { | ||
| "pattern": "SPAKE2+", |
| ] | ||
| }, | ||
| { | ||
| "family": "SPAKE2PLUS", |
Contributor
There was a problem hiding this comment.
nit: does it make sense to also call it SPAKE2+ to match the patterns?
…DX#797) Signed-off-by: Mehrn0ush <mehrnoush.vaseghi@gmail.com>
Mehrn0ush
force-pushed
the
feat/crypto-registry-spake2-rfc9382-rfc9383
branch
from
372b928 to
6cd1973
Compare
Contributor
Author
|
Thanks @bhess ! Agreed — I’ll remove the plain SPAKE2 and SPAKE2+ variants. Re: family naming — I kept SPAKE2PLUS (no +) to align with existing registry family identifiers, while preserving the canonical protocol name SPAKE2+ in the variant pattern per RFC 9383. If you’d prefer family: "SPAKE2+" for consistency with the canonical name, I’m happy to update it — I kept SPAKE2PLUS only because the current registry doesn’t appear to use + in family identifiers. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add SPAKE2 (RFC 9382) and SPAKE2+ (RFC 9383) to
schema/cryptography-defs.json.References
Change
family: SPAKE2with variants:SPAKE2SPAKE2[-{group}][-{hashFunction}][-{kdf}][-{mac}]family: SPAKE2PLUS(represents SPAKE2+) with variants:SPAKE2+SPAKE2+[-{group}][-{hashFunction}][-{kdf}][-{mac}]Notes:
familyusesSPAKE2PLUS(no+) to match existing registry naming constraints, whilepatternpreserves the canonical protocol nameSPAKE2+from RFC 9383.algorithms[].Validation
python3 -m json.tool schema/cryptography-defs.json(JSON OK)